Importing camera paths in Lumion - how it would work and why it is yet to be implemented.
From Marius GChat Monday 30/11/2020
- it's difficult to fit into Lumion's current structure/workflow
- if we support .FBX, people will ask about the 100 other filetypes that also support camera paths and we'll have to very carefully navigate that.
Also, not everything in .FBXx camera animation can be used, things like FOV has to be converted to Lumion's camera mm, and only certain aspects can be used, like position, rotation, the field of view (but which one? the horizontal? the vertical?). Time has to be converted if it's there. If its just frames, we'll have to convert it, but only when fps is specified otherwise we have to choose something. And its always going to be wrong. If there are more than 1 camera in the file, we'll have to either let the user pick one or always take the first one. Letting them pick is nicer, but about 500% more work for us on UI/UX/coding
We'll definitely put it on the list ofc, but as always, no guarantees that it makes the final feature list for 12.
The difficult part isn't even the technical implementation, but rather how to make it fit into Lumion.
With the ortho camera though, doors have been opened that make this a little more feasible.